Skip to content

Conversation

@dnut
Copy link
Contributor

@dnut dnut commented Oct 1, 2025

This adds conformance/commits.env with a commit hash of every repo used for testing sig's conformance with agave.

It's important that these commits are the same commits that we're using in CI. Anyone should be able to easily check out our code and run conformance locally by using these commit hashes, with high confidence that everything will work and be conformant with the code we have on main.

For SOLANA_CONFORMANCE_COMMIT and TEST_VECTORS_COMMIT, I changed the CI to ensure these are always pulled in directly from commits.env and used to check out the actual code used in CI.

For the other commits, this is not possible since the artifacts are pre-generated and not checked out within CI. So I added a basic script to grep files for where these commit hashes are documented or used for other purposes, and set it up to run this verification script in CI. It isn't a foolproof check, but at least it will flag some inconsistencies. The first run detected an inconsistency that we have on main which I fixed in 1434e9d.

@github-project-automation github-project-automation bot moved this to 🏗 In progress in Sig Oct 1, 2025
@dnut dnut requested a review from Rexicon226 October 1, 2025 13:11
@dnut dnut marked this pull request as ready for review October 1, 2025 13:11
@dnut dnut requested review from ultd and yewman as code owners October 1, 2025 13:11
@codecov
Copy link

codecov bot commented Oct 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@Rexicon226 Rexicon226 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just have the circleci use these variables, instead of checking they exist inside of the config? This seems very roundabout to me.

@github-project-automation github-project-automation bot moved this from 🏗 In progress to 👀 In review in Sig Oct 1, 2025
@dnut dnut requested a review from Rexicon226 October 1, 2025 14:47
Rexicon226
Rexicon226 previously approved these changes Oct 5, 2025
yewman
yewman previously approved these changes Oct 7, 2025
@dnut dnut added this pull request to the merge queue Oct 7, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Oct 7, 2025
@dnut dnut dismissed stale reviews from yewman and Rexicon226 via 9f11e60 October 8, 2025 20:13
@dnut dnut requested review from Rexicon226 and yewman October 8, 2025 20:13
@dnut dnut enabled auto-merge October 8, 2025 20:15
@dnut dnut added this pull request to the merge queue Oct 9, 2025
Merged via the queue into main with commit e975dad Oct 9, 2025
18 checks passed
@dnut dnut deleted the dnut/conformance/commits.env branch October 9, 2025 21:56
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Sig Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

4 participants